PROFINET Core
Bugs:
- PSPNCORE-387: Submodule diagnosis status not updated properly when receiving alarm
Changes:
Changes:
New Features:
- PSPNCORE-263: Support finishing a DCP Identify sequence after first response
Bugs:
- PSPNCORE-265: DrvEth adapter for PnD/PnC switch returns wrong valid flags for port statistics
Changes:
Bugs:
- PSPNCORE-247: Transmit confirmation of multicast frames may be reported twice
Changes:
Bugs:
- PSPNCORE-208: Controller PPM might send inconsistent or old process data
Bugs:
- PSPNCORE-201: Unexpected use of receive timestamp.
- PSPNCORE-197: Unexpected CPM/PPM timer stop
- PSPNCORE-194: Unexpected alarm error detected
- PSPNCORE-193: Bad value for Hardwarerevision in SNMP System description if value is greater than 99
New Features:
- PSPNCORE-167: Feature: Add support for Second Chassis MAC Address to PnC HAL
Changes:
Bugs:
- PSPNCORE-172: Reading lldpXPnoLocLPDValue and lldpXPnoRemLPDValue Mib's returns wrong values
- PSPNCORE-165: LLDP EXT DOT 3 MIB not enabled
- PSPNCORE-163: DCP SuboptionDeviceOption list contains "OEM Device ID" even if I&M5 not supported
- PSPNCORE-150: PND FDB not working due to linking issue
- PSPNCORE-148: Ethernet frame buffer not released when invalid DCP Get Request received
Bugs:
- PSPNCORE-201: Unexpected use of receive timestamp.
- PSPNCORE-194: Unexpected alarm error detected
- PSPNCORE-193: Bad value for Hardwarerevision in SNMP System description if value is greater than 99
Bugs:
- PSPNCORE-172: Reading lldpXPnoLocLPDValue and lldpXPnoRemLPDValue Mib's returns wrong values
Bugs:
Bugs:
- PSPNCORE-163: DCP SuboptionDeviceOption list contains "OEM Device ID" even if I&M5 not supported
Changes:
Bugs:
- PSPNCORE-150: PND FDB not working due to linking issue
- PSPNCORE-148: Ethernet frame buffer not released when invalid DCP Get Request received
Changes:
Bugs:
New Features:
Bugs:
Bugs:
Changes:
Bugs:
- PSPNCORE-172: Reading lldpXPnoLocLPDValue and lldpXPnoRemLPDValue Mib's returns wrong values
Bugs:
Changes:
Bugs:
- PSPNCORE-148: Ethernet frame buffer not released when invalid DCP Get Request received
- PSPNCORE-146: Task identifier of RTC task not set
- PSPNCORE-145: Invalid values reported in Profinet MIB
- PSPNCORE-144: PTCP PLL not reset if synchronization lost
- PSPNCORE-141: Wrong sync send interval for sendclock 128
- PSPNCORE-133: Alarm Notification Ind not checked properly
New Features:
Bugs:
- PSPNCORE-130: sometimes the rtc scheduler skips sending of RT-frames
New Features:
Changes:
- PSPNCORE-121: Detect and indicate IOCS changes from bad to good
New Features:
- PSPNCORE-115: Introduce new IO callback to provide IO timing information
- PSPNCORE-114: Support DCP OEM Device ID
- PSPNCORE-76: Implement Media Redundancy Manager (MRM) statemachine
Changes:
Bugs:
- PSPNCORE-116: RPC Memory cleared when extending PDU
- PSPNCORE-113: Unexpected DCP Set response in case of invalid request syntax or suboption parameters
- PSPNCORE-111: Diagnosis database not thread safe
- PSPNCORE-109: Diagnosis record database not ordered properly according subslot, ChannelNumber and Userstructure identifier
- PSPNCORE-107: Invalid memory access
- PSPNCORE-106: DCP request with large amount of data corrupts the Name of station
- PSPNCORE-105: Systime timing deadlock on netX50
Bugs:
- PSPNCORE-130: sometimes the rtc scheduler skips sending of RT-frames
- PSPNCORE-116: RPC Memory cleared when extending PDU
- PSPNCORE-113: Unexpected DCP Set response in case of invalid request syntax or suboption parameters
Bugs:
- PSPNCORE-109: Diagnosis record database not ordered properly according subslot, ChannelNumber and Userstructure identifier
- PSPNCORE-107: Invalid memory access
Bugs:
- PSPNCORE-106: DCP request with large amount of data corrupts the Name of station
- PSPNCORE-105: Systime timing deadlock on netX50
Bugs:
- PSPNCORE-100: wrong ExtendedChannelErrorType reported in case of link down (certification issue)
- PSPNCORE-99: wrong LLDP-PortID in case of MultipleInterfaceMode (certification issue)
Bugs:
- PSPNCORE-93: Cycle Control not disabled if sync is lost
Bugs:
- PSPNCORE-92: First synchronization after powercycle fails
- PSPNCORE-91: Receive data not cleared properly on CPM timeout
- PSPNCORE-90: Invalid cycle counter & time in PTCP Sync Frame
Bugs:
- PSPNCORE-148: Ethernet frame buffer not released when invalid DCP Get Request received
Bugs:
Bugs:
- PSPNCORE-130: sometimes the rtc scheduler skips sending of RT-frames
Bugs:
Bugs:
- PSPNCORE-113: Unexpected DCP Set response in case of invalid request syntax or suboption parameters
Bugs:
Bugs:
- PSPNCORE-100: wrong ExtendedChannelErrorType reported in case of link down (certification issue)
- PSPNCORE-99: wrong LLDP-PortID in case of MultipleInterfaceMode (certification issue)
Bugs:
- PSPNCORE-93: Cycle Control not disabled if sync is lost
- PSPNCORE-92: First synchronization after powercycle fails
- PSPNCORE-91: Receive data not cleared properly on CPM timeout
- PSPNCORE-90: Invalid cycle counter & time in PTCP Sync Frame
Changes:
- PSPNCORE-72: Set management OID in LLDP Management TLV to null
- PSPNCORE-71: Validate DCP Set Req in DCPUCR before applying the request
Bugs:
- PSPNCORE-89: fix issues uncovered by SPIRTA
- PSPNCORE-74: SNMP-access: XPno NameOfStation shall be format as visible mac address